Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e9d148bbd4c430e2aacf5e588e4a63d9f78aa8018f318d5e0e41d0a3406c2d0

Tx prefix hash: b95c8461279efa71ccd5e448e52496e649289418c9b6252ff84e8e2d8e477160
Tx public key: a6a1d4ea969cd510a730bf1349ae20e89bbb915cb3167587173dd9df0d60913c
Timestamp: 1760441269 Timestamp [UCT]: 2025-10-14 11:27:49 Age [y:d:h:m:s]: 00:038:08:14:35
Block: 1389717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27452 RingCT/type: yes/0
Extra: 01a6a1d4ea969cd510a730bf1349ae20e89bbb915cb3167587173dd9df0d60913c0211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a7d07e86ba14fb2d4ca2a246e6282ff24a997ffdc57a31aa930e6f404b7201b 0.600000000000 1877946 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": 1389727, "vin": [ { "gen": { "height": 1389717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a7d07e86ba14fb2d4ca2a246e6282ff24a997ffdc57a31aa930e6f404b7201b" } } ], "extra": [ 1, 166, 161, 212, 234, 150, 156, 213, 16, 167, 48, 191, 19, 73, 174, 32, 232, 155, 187, 145, 92, 179, 22, 117, 135, 23, 61, 217, 223, 13, 96, 145, 60, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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