Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a3f6398d22f59f029a5c2a20658ae9b46d52a65234cc41a59f7a368da18caa

Tx prefix hash: f199097342d4fb4e8172e71f4a98c267d8707b61f4e506611b6d362cfa51559f
Tx public key: ba5156106fbe0103df1a7440c993c526877bd7889b036b0e283701570a0b5824
Timestamp: 1718553253 Timestamp [UCT]: 2024-06-16 15:54:13 Age [y:d:h:m:s]: 00:222:01:36:37
Block: 1045577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158851 RingCT/type: yes/0
Extra: 01ba5156106fbe0103df1a7440c993c526877bd7889b036b0e283701570a0b582402110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbc7f141478c3b2646698a0274d9b8f5f9444fff8e98af01da9bdae8ff53b113 0.600000000000 1515184 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": 1045587, "vin": [ { "gen": { "height": 1045577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbc7f141478c3b2646698a0274d9b8f5f9444fff8e98af01da9bdae8ff53b113" } } ], "extra": [ 1, 186, 81, 86, 16, 111, 190, 1, 3, 223, 26, 116, 64, 201, 147, 197, 38, 135, 123, 215, 136, 155, 3, 107, 14, 40, 55, 1, 87, 10, 11, 88, 36, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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