Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6fb488a9aec9b7983d26efe2ff108c21de8cd76c75bfd0e1360522cc26d41df

Tx prefix hash: a4be2666d2a4f769b355a9f60deff2b292ca8132f69da0dc0fab61560cfd7219
Tx public key: e84a6df87b5ac36fcfd06041d07e18392b00fa704049144b242e286d4e5190a9
Timestamp: 1764878627 Timestamp [UCT]: 2025-12-04 20:03:47 Age [y:d:h:m:s]: 00:018:21:42:46
Block: 1426508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13512 RingCT/type: yes/0
Extra: 01e84a6df87b5ac36fcfd06041d07e18392b00fa704049144b242e286d4e5190a9021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f747c7727988076af3be935d1a627c53a1089301f94fa7367d0cfc39ac37151 0.600000000000 1915199 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": 1426518, "vin": [ { "gen": { "height": 1426508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f747c7727988076af3be935d1a627c53a1089301f94fa7367d0cfc39ac37151" } } ], "extra": [ 1, 232, 74, 109, 248, 123, 90, 195, 111, 207, 208, 96, 65, 208, 126, 24, 57, 43, 0, 250, 112, 64, 73, 20, 75, 36, 46, 40, 109, 78, 81, 144, 169, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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