Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7e789c9b206fc74f67c3c215bcba67fc1bffe349a8950ab574e3124b3d7e4c0

Tx prefix hash: 4d267e7984dae3c981e7cb5e9cb16a35a018b85a654eca0eab649fa13a2777ce
Tx public key: e5811547648b6963cefd9e1e06d4ead9dd4678e3283d9d412cc39cfea8b323d4
Timestamp: 1759420855 Timestamp [UCT]: 2025-10-02 16:00:55 Age [y:d:h:m:s]: 00:096:05:45:01
Block: 1381250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68921 RingCT/type: yes/0
Extra: 01e5811547648b6963cefd9e1e06d4ead9dd4678e3283d9d412cc39cfea8b323d402110000000b97baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01e20966006daeb2197ec2e665896c021c55df2d8ba838e7628fa15f2134e807 0.600000000000 1869369 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": 1381260, "vin": [ { "gen": { "height": 1381250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01e20966006daeb2197ec2e665896c021c55df2d8ba838e7628fa15f2134e807" } } ], "extra": [ 1, 229, 129, 21, 71, 100, 139, 105, 99, 206, 253, 158, 30, 6, 212, 234, 217, 221, 70, 120, 227, 40, 61, 157, 65, 44, 195, 156, 254, 168, 179, 35, 212, 2, 17, 0, 0, 0, 11, 151, 186, 249, 34, 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