Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9ad7dd2543e94e4f98fca71a681e25c409718299dc1ba47f1153c298102e4dc

Tx prefix hash: 9dd57c78fc8c3cbbef57eb5cee5334ae9f73166ce1df96eac0ccd877f54ab7db
Tx public key: 38c7047c46b247f61b9052a75dfcdd406044296d1d1403dc6b20e901326b73b3
Timestamp: 1747101777 Timestamp [UCT]: 2025-05-13 02:02:57 Age [y:d:h:m:s]: 00:188:09:16:09
Block: 1281707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132347 RingCT/type: yes/0
Extra: 0138c7047c46b247f61b9052a75dfcdd406044296d1d1403dc6b20e901326b73b30211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae4f468180600a6e7e6efffbbdbf99d0c9addbc89396ae8a94a9e456a3b770f9 0.600000000000 1769110 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": 1281717, "vin": [ { "gen": { "height": 1281707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae4f468180600a6e7e6efffbbdbf99d0c9addbc89396ae8a94a9e456a3b770f9" } } ], "extra": [ 1, 56, 199, 4, 124, 70, 178, 71, 246, 27, 144, 82, 167, 93, 252, 221, 64, 96, 68, 41, 109, 29, 20, 3, 220, 107, 32, 233, 1, 50, 107, 115, 179, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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