Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ac0a54a3aac822c9e198802fae878dfa17e739ae77ed49a673c33d08a123d8df

Tx prefix hash: 4fbb47ffb9cc0b733d98297be20571972b8c94df3c7c8400a328b4fc87180f60
Tx public key: 6b7fb483de6ddb76cbacfd861433b12600806bb791ddc63ea3ebbae683f8a14e
Timestamp: 1702911713 Timestamp [UCT]: 2023-12-18 15:01:53 Age [y:d:h:m:s]: 00:341:22:59:53
Block: 915889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244846 RingCT/type: yes/0
Extra: 016b7fb483de6ddb76cbacfd861433b12600806bb791ddc63ea3ebbae683f8a14e02110000001075e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89dc3d27fe8df6cb2c70c6566cd8472ad508cbba018b147054f282e44b2499c7 0.600000000000 1373323 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 915899, "vin": [ { "gen": { "height": 915889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89dc3d27fe8df6cb2c70c6566cd8472ad508cbba018b147054f282e44b2499c7" } } ], "extra": [ 1, 107, 127, 180, 131, 222, 109, 219, 118, 203, 172, 253, 134, 20, 51, 177, 38, 0, 128, 107, 183, 145, 221, 198, 62, 163, 235, 186, 230, 131, 248, 161, 78, 2, 17, 0, 0, 0, 16, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8