Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa08ef996d3f843fabfe1cdbc5ca907f3a0df735774797d6923f00c8c5dd51a

Tx prefix hash: 9d98148afd58be3e6c1ca7c55ad4419ecbdedbb6e5398d968571b536444f39ec
Tx public key: ba632ac3886a7ea1720de52e8c626ae5dc1a5b5bd5b3442a3496f04cc5b0627d
Timestamp: 1744067867 Timestamp [UCT]: 2025-04-07 23:17:47 Age [y:d:h:m:s]: 00:188:20:07:06
Block: 1256580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132667 RingCT/type: yes/0
Extra: 01ba632ac3886a7ea1720de52e8c626ae5dc1a5b5bd5b3442a3496f04cc5b0627d021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2620ff42b7b122a230cad6b4644e2605a7534c63075edd9a2275aeaec78157ba 0.600000000000 1743695 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": 1256590, "vin": [ { "gen": { "height": 1256580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2620ff42b7b122a230cad6b4644e2605a7534c63075edd9a2275aeaec78157ba" } } ], "extra": [ 1, 186, 99, 42, 195, 136, 106, 126, 161, 114, 13, 229, 46, 140, 98, 106, 229, 220, 26, 91, 91, 213, 179, 68, 42, 52, 150, 240, 76, 197, 176, 98, 125, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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