Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4de1fb88922a0e9f94bba4fb708a6770ad20796ae51e8fd33e6154d82e68510

Tx prefix hash: 1c1e8b2bc6d0a814b59110835b94a665668a28e79449c28cf98033da275bb171
Tx public key: 7bc970c948cf239a5c7d554fe8470020d6177ecb6d927efca20d3dae6487f98e
Timestamp: 1670942430 Timestamp [UCT]: 2022-12-13 14:40:30 Age [y:d:h:m:s]: 02:040:09:15:37
Block: 651747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550731 RingCT/type: yes/0
Extra: 017bc970c948cf239a5c7d554fe8470020d6177ecb6d927efca20d3dae6487f98e0211000000047e406890000000000000000000

1 output(s) for total of 4.251005041000 dcy

stealth address amount amount idx
00: 6ec769b64bd7e3d46423783fdcaf40f53cdf5fbfa39339a02dce2c7c0c8bc531 4.251005041000 1092164 of 0

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": 651757, "vin": [ { "gen": { "height": 651747 } } ], "vout": [ { "amount": 4251005041, "target": { "key": "6ec769b64bd7e3d46423783fdcaf40f53cdf5fbfa39339a02dce2c7c0c8bc531" } } ], "extra": [ 1, 123, 201, 112, 201, 72, 207, 35, 154, 92, 125, 85, 79, 232, 71, 0, 32, 214, 23, 126, 203, 109, 146, 126, 252, 162, 13, 61, 174, 100, 135, 249, 142, 2, 17, 0, 0, 0, 4, 126, 64, 104, 144, 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