Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d391fe87b6526e7acb7eb7ce7c8d2e1df029be21fbf7716ac5333ddfccf32818

Tx prefix hash: 26e50dbbcb735632ded3d6f7f5a400fc60c916803a2fc663a035bcc6a05dfbed
Tx public key: db7eaca3daf1b68dc20016e36a023623d5da6a5d1a2f45645d514ae0d406151d
Timestamp: 1745976967 Timestamp [UCT]: 2025-04-30 01:36:07 Age [y:d:h:m:s]: 00:245:17:48:38
Block: 1272409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173398 RingCT/type: yes/0
Extra: 01db7eaca3daf1b68dc20016e36a023623d5da6a5d1a2f45645d514ae0d406151d02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52495b08027309201c69a81604089f7fbe35a26be065c806fda03c4923e345b3 0.600000000000 1759684 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": 1272419, "vin": [ { "gen": { "height": 1272409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52495b08027309201c69a81604089f7fbe35a26be065c806fda03c4923e345b3" } } ], "extra": [ 1, 219, 126, 172, 163, 218, 241, 182, 141, 194, 0, 22, 227, 106, 2, 54, 35, 213, 218, 106, 93, 26, 47, 69, 100, 93, 81, 74, 224, 212, 6, 21, 29, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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