Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32fd00eba5b832e72c8a2be61cb4b5c6a79db4a8e243f97906341f9a955215b0

Tx prefix hash: d81b1d98829cd3dcce891f77db3c3ec9bd974c56decd359e8a5c4c715f5708f1
Tx public key: a04c987565754af5e7c7ca46fdc2903d3e3215403233384be87f1476f0b8f7da
Timestamp: 1757767340 Timestamp [UCT]: 2025-09-13 12:42:20 Age [y:d:h:m:s]: 00:110:09:02:55
Block: 1367556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79033 RingCT/type: yes/0
Extra: 01a04c987565754af5e7c7ca46fdc2903d3e3215403233384be87f1476f0b8f7da021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2cb0f8a386409bb4d6c9095ff533977880059df1c73a2dbf472ea3ded0e6f6a 0.600000000000 1855595 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": 1367566, "vin": [ { "gen": { "height": 1367556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2cb0f8a386409bb4d6c9095ff533977880059df1c73a2dbf472ea3ded0e6f6a" } } ], "extra": [ 1, 160, 76, 152, 117, 101, 117, 74, 245, 231, 199, 202, 70, 253, 194, 144, 61, 62, 50, 21, 64, 50, 51, 56, 75, 232, 127, 20, 118, 240, 184, 247, 218, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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