Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe409e7797077e318da7ad6c88cd4442f9d6d2bc521ac26e644be74affc6362

Tx prefix hash: 68a52da8e38e2d15d0f3d4d044cd68aebddd40de368e1afbba5d2b8b617232ad
Tx public key: 7a2864b0ddded3cd159c6845ec1d640004035ed7dff07a17ccb939b831cf8474
Timestamp: 1751478113 Timestamp [UCT]: 2025-07-02 17:41:53 Age [y:d:h:m:s]: 00:141:15:49:08
Block: 1317372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99482 RingCT/type: yes/0
Extra: 017a2864b0ddded3cd159c6845ec1d640004035ed7dff07a17ccb939b831cf8474021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b032398272f2c3634df5ce0610185bde0c1b2b618aaf59c6d9014f6a44f6ae 0.600000000000 1805039 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": 1317382, "vin": [ { "gen": { "height": 1317372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b032398272f2c3634df5ce0610185bde0c1b2b618aaf59c6d9014f6a44f6ae" } } ], "extra": [ 1, 122, 40, 100, 176, 221, 222, 211, 205, 21, 156, 104, 69, 236, 29, 100, 0, 4, 3, 94, 215, 223, 240, 122, 23, 204, 185, 57, 184, 49, 207, 132, 116, 2, 17, 0, 0, 0, 9, 191, 81, 178, 162, 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