Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77f6d7478bcdf686c178e66b9c9500f38dc4f1e967b7000b1cc412ba9564bb88

Tx prefix hash: f0775d5235e94738dddabe3aee5d1b7849986224452b57b32da56b8c925e39ce
Tx public key: 322e290f9eae19a7b47befc4b55ee799d54e2fbb1ba003f517a8bfadf6f67800
Timestamp: 1738186705 Timestamp [UCT]: 2025-01-29 21:38:25 Age [y:d:h:m:s]: 00:328:04:17:41
Block: 1207915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232344 RingCT/type: yes/0
Extra: 01322e290f9eae19a7b47befc4b55ee799d54e2fbb1ba003f517a8bfadf6f67800021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5381eec4f6bd300ecec06f365223a5ce8a97f119c5e0f4d9cee55d8ca82c264 0.600000000000 1694642 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": 1207925, "vin": [ { "gen": { "height": 1207915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5381eec4f6bd300ecec06f365223a5ce8a97f119c5e0f4d9cee55d8ca82c264" } } ], "extra": [ 1, 50, 46, 41, 15, 158, 174, 25, 167, 180, 123, 239, 196, 181, 94, 231, 153, 213, 78, 47, 187, 27, 160, 3, 245, 23, 168, 191, 173, 246, 246, 120, 0, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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