Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0b4bead4609e5811e3e9f126ad53639e575852b80d8aeebd501641e3d976c3

Tx prefix hash: 989e8cd42e9a5967c01b44d6fceb4be962a55118093ba5fae2c667bfd6f94e45
Tx public key: 9ad418b5a8053c0e416b6991c1c0a6977e0ba7448988570225f9ee9dde6358e4
Timestamp: 1736089914 Timestamp [UCT]: 2025-01-05 15:11:54 Age [y:d:h:m:s]: 00:164:09:16:03
Block: 1190821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117187 RingCT/type: yes/0
Extra: 019ad418b5a8053c0e416b6991c1c0a6977e0ba7448988570225f9ee9dde6358e40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a23adfe7c0ccd2f76d2023b0a0de4c93f462689713a4758acc03a122bcf7841a 0.600000000000 1677340 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": 1190831, "vin": [ { "gen": { "height": 1190821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a23adfe7c0ccd2f76d2023b0a0de4c93f462689713a4758acc03a122bcf7841a" } } ], "extra": [ 1, 154, 212, 24, 181, 168, 5, 60, 14, 65, 107, 105, 145, 193, 192, 166, 151, 126, 11, 167, 68, 137, 136, 87, 2, 37, 249, 238, 157, 222, 99, 88, 228, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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