Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18b4c9461d869c4c12f73954ddc2d3a774edcef8b7c536279f72d3eb2c3a942c

Tx prefix hash: 2733256291a12d7611671ec43fff4ac2ea7f6d39aca5e115a2d5d9c990d406e7
Tx public key: 963877db770def01a26e4dec2f2bfdd586ed118412fb7ce0a393cc17c4cd67e1
Timestamp: 1727173598 Timestamp [UCT]: 2024-09-24 10:26:38 Age [y:d:h:m:s]: 00:120:05:23:01
Block: 1117031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85916 RingCT/type: yes/0
Extra: 01963877db770def01a26e4dec2f2bfdd586ed118412fb7ce0a393cc17c4cd67e102110000000191e13c04000000000000000000

1 output(s) for total of 0.607990000000 dcy

stealth address amount amount idx
00: a54f3d9d70863e072caccd1aef9dd6a6a3b29ebf3930ec942fcea0a786a880e5 0.607990000000 1597718 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": 1117041, "vin": [ { "gen": { "height": 1117031 } } ], "vout": [ { "amount": 607990000, "target": { "key": "a54f3d9d70863e072caccd1aef9dd6a6a3b29ebf3930ec942fcea0a786a880e5" } } ], "extra": [ 1, 150, 56, 119, 219, 119, 13, 239, 1, 162, 110, 77, 236, 47, 43, 253, 213, 134, 237, 17, 132, 18, 251, 124, 224, 163, 147, 204, 23, 196, 205, 103, 225, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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