Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d3391bc4e2c613c68846a4ae71ac81499c2e0281cce67cac8cdf9514a539870

Tx prefix hash: d5b19e585b23d616315ce36c0c9b158b848bda63b43b50a0950c39a7d1341dc7
Tx public key: 7f4a932c08310eea998f482ab0bcc74234a3b761e8e1935add391239f5033f82
Timestamp: 1739257683 Timestamp [UCT]: 2025-02-11 07:08:03 Age [y:d:h:m:s]: 00:327:08:53:03
Block: 1216770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231811 RingCT/type: yes/0
Extra: 017f4a932c08310eea998f482ab0bcc74234a3b761e8e1935add391239f5033f820211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaab37c30631e3d9b7dcbfa32059d0c8684ce24ee330a7f3ed9205cafe7cf500 0.600000000000 1703577 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": 1216780, "vin": [ { "gen": { "height": 1216770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaab37c30631e3d9b7dcbfa32059d0c8684ce24ee330a7f3ed9205cafe7cf500" } } ], "extra": [ 1, 127, 74, 147, 44, 8, 49, 14, 234, 153, 143, 72, 42, 176, 188, 199, 66, 52, 163, 183, 97, 232, 225, 147, 90, 221, 57, 18, 57, 245, 3, 63, 130, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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