Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09d6bc8823183498ccf7f099a6de75dcfbd2ee3ef92e02a316ab9f456a706232

Tx prefix hash: bcb0ec4fbf3812d51b87ad249213233ec65e4d5af0bfa768a79cb49882f53181
Tx public key: f7c3a6bba451bf2e86067c9265980fcf6cb6024df480516e0e8da023953a08dd
Timestamp: 1725590858 Timestamp [UCT]: 2024-09-06 02:47:38 Age [y:d:h:m:s]: 00:221:18:30:26
Block: 1103904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158353 RingCT/type: yes/0
Extra: 01f7c3a6bba451bf2e86067c9265980fcf6cb6024df480516e0e8da023953a08dd02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af412220bb2c94bb144a8bc5b3f786933c9fede075260b66a88e7d1e554d8524 0.600000000000 1580915 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": 1103914, "vin": [ { "gen": { "height": 1103904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af412220bb2c94bb144a8bc5b3f786933c9fede075260b66a88e7d1e554d8524" } } ], "extra": [ 1, 247, 195, 166, 187, 164, 81, 191, 46, 134, 6, 124, 146, 101, 152, 15, 207, 108, 182, 2, 77, 244, 128, 81, 110, 14, 141, 160, 35, 149, 58, 8, 221, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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