Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5923dfd91aabcb021481ae6b7529db55d0d48f7f6561db31514dd30943aaa68

Tx prefix hash: a4f9d17de8d3dc7c676cfacdd0f3e7c6ead2310145be132733b5455091a35ae9
Tx public key: 6f1f019500b96bcc5785e4a9793eabd223d30794e7c44aa5e9bdb298df4a9c53
Timestamp: 1720554932 Timestamp [UCT]: 2024-07-09 19:55:32 Age [y:d:h:m:s]: 00:297:19:12:57
Block: 1062156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212785 RingCT/type: yes/0
Extra: 016f1f019500b96bcc5785e4a9793eabd223d30794e7c44aa5e9bdb298df4a9c5302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72fb4f4d66c0fe64d7d6f70a28f20b57c0d2a7bb56a5455e0f3dcbf8a82a9a34 0.600000000000 1532657 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": 1062166, "vin": [ { "gen": { "height": 1062156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72fb4f4d66c0fe64d7d6f70a28f20b57c0d2a7bb56a5455e0f3dcbf8a82a9a34" } } ], "extra": [ 1, 111, 31, 1, 149, 0, 185, 107, 204, 87, 133, 228, 169, 121, 62, 171, 210, 35, 211, 7, 148, 231, 196, 74, 165, 233, 189, 178, 152, 223, 74, 156, 83, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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