Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 829d8b3e540c57e53fc1fa2625ab83d70ff068903685552291dd2cc2829b19ad

Tx prefix hash: 4fefbf71b59685b1749da19193a09b8014c2f44d95515a6534490e4abf1b1bc6
Tx public key: 1cd0235edea0b93561626fa4cb5c5788c8efcba85ca72d32df3af4d81a5b69cb
Timestamp: 1763528496 Timestamp [UCT]: 2025-11-19 05:01:36 Age [y:d:h:m:s]: 00:009:01:24:46
Block: 1415298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6489 RingCT/type: yes/0
Extra: 011cd0235edea0b93561626fa4cb5c5788c8efcba85ca72d32df3af4d81a5b69cb0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dfc989d1fc4e57edf3d7e9486e2491e6687fd6aee8306ec1dfb5b0798f942d0 0.600000000000 1903799 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": 1415308, "vin": [ { "gen": { "height": 1415298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dfc989d1fc4e57edf3d7e9486e2491e6687fd6aee8306ec1dfb5b0798f942d0" } } ], "extra": [ 1, 28, 208, 35, 94, 222, 160, 185, 53, 97, 98, 111, 164, 203, 92, 87, 136, 200, 239, 203, 168, 92, 167, 45, 50, 223, 58, 244, 216, 26, 91, 105, 203, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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