Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17cf34c310c01a35042c39fcf0926673fca3ccf0bfafd04b22687c10bb7cbe98

Tx prefix hash: 140df3083efd09d20ac2cd9f6255a038e3bcc1118a9e0f17aa371d3f2c7d8454
Tx public key: 59cf63a427c5c0e83becb5575d3adb7c9bbfe3b58213d14cd6e3f6af251e09dd
Timestamp: 1746156723 Timestamp [UCT]: 2025-05-02 03:32:03 Age [y:d:h:m:s]: 00:203:04:14:39
Block: 1273885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142915 RingCT/type: yes/0
Extra: 0159cf63a427c5c0e83becb5575d3adb7c9bbfe3b58213d14cd6e3f6af251e09dd02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31bc2a894f3ceafcc016365e3cdea28d57f642ef7fbe0106010d6891daa9f784 0.600000000000 1761172 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": 1273895, "vin": [ { "gen": { "height": 1273885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31bc2a894f3ceafcc016365e3cdea28d57f642ef7fbe0106010d6891daa9f784" } } ], "extra": [ 1, 89, 207, 99, 164, 39, 197, 192, 232, 59, 236, 181, 87, 93, 58, 219, 124, 155, 191, 227, 181, 130, 19, 209, 76, 214, 227, 246, 175, 37, 30, 9, 221, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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