Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a03f593901e774991ede95c8f96e68fb1b91f79d3cea7084c72b480a7469a4ce

Tx prefix hash: 2bd66f821cee0c00ae425d1c37605bb6f3844622b1852e82cc5cc5e233ddc6b6
Tx public key: 0b9ec855e99d927f9a88cd30952876d39599fd26f27ffce8fcaa0bd16e1940cd
Timestamp: 1747359528 Timestamp [UCT]: 2025-05-16 01:38:48 Age [y:d:h:m:s]: 00:189:13:03:31
Block: 1283835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133178 RingCT/type: yes/0
Extra: 010b9ec855e99d927f9a88cd30952876d39599fd26f27ffce8fcaa0bd16e1940cd021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a15699843155dc1db4bcdc694e1cd156dcdae94ff8f7ec8b14b8eafdd5ce6e2c 0.600000000000 1771254 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": 1283845, "vin": [ { "gen": { "height": 1283835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a15699843155dc1db4bcdc694e1cd156dcdae94ff8f7ec8b14b8eafdd5ce6e2c" } } ], "extra": [ 1, 11, 158, 200, 85, 233, 157, 146, 127, 154, 136, 205, 48, 149, 40, 118, 211, 149, 153, 253, 38, 242, 127, 252, 232, 252, 170, 11, 209, 110, 25, 64, 205, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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