Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63efb163c2dd77c6d3831eeaacf3170e1bc27d835a0b647420fcd2e7a0832eca

Tx prefix hash: f7130944b91314744ea4e73b38868889bdf2df762f8f0a7f275761517d545713
Tx public key: 468d09ab44326dcb8894119f958d23a9e473b11a2557eb66a4b54c9a13a17101
Timestamp: 1752745651 Timestamp [UCT]: 2025-07-17 09:47:31 Age [y:d:h:m:s]: 00:169:21:56:20
Block: 1327327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120284 RingCT/type: yes/0
Extra: 01468d09ab44326dcb8894119f958d23a9e473b11a2557eb66a4b54c9a13a17101021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87d406c8915e4e10121d638f2d1cbf5f24e5d135a39a012e1c2089625a7172b3 0.600000000000 1815082 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": 1327337, "vin": [ { "gen": { "height": 1327327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87d406c8915e4e10121d638f2d1cbf5f24e5d135a39a012e1c2089625a7172b3" } } ], "extra": [ 1, 70, 141, 9, 171, 68, 50, 109, 203, 136, 148, 17, 159, 149, 141, 35, 169, 228, 115, 177, 26, 37, 87, 235, 102, 164, 181, 76, 154, 19, 161, 113, 1, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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