Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59d09bbb8b55ad452264bddb049986c4cb2cfbd4ff6a72736f9ece218511a5cd

Tx prefix hash: de7969f7f03fd38f1a9da09709f159c94d1ebc71f85c77fc8560c52634a40f82
Tx public key: ff03651c8d02c735aa96cbe046ceabfdc1a0c318be0cd78bc1d9c7516043f4aa
Timestamp: 1736031059 Timestamp [UCT]: 2025-01-04 22:50:59 Age [y:d:h:m:s]: 00:165:13:06:45
Block: 1190336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117993 RingCT/type: yes/0
Extra: 01ff03651c8d02c735aa96cbe046ceabfdc1a0c318be0cd78bc1d9c7516043f4aa021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2be168c6d3d55a7ae15bc0489c4f77292c1968e1ed9be7240e38b2e52ef7d2a9 0.600000000000 1676851 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": 1190346, "vin": [ { "gen": { "height": 1190336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2be168c6d3d55a7ae15bc0489c4f77292c1968e1ed9be7240e38b2e52ef7d2a9" } } ], "extra": [ 1, 255, 3, 101, 28, 141, 2, 199, 53, 170, 150, 203, 224, 70, 206, 171, 253, 193, 160, 195, 24, 190, 12, 215, 139, 193, 217, 199, 81, 96, 67, 244, 170, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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