Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c56ba9bbaf604caeaf53fdee79d6e0d9b6eca2933f4d7f3a892dda172ac4b3

Tx prefix hash: 9ba8fe67cc851dd5909ad1213933143aa04fe57a1b33d5da5fd638eb19753070
Tx public key: 568d8b89ed95c9b004c51c72a3f3299369c9d49a28a04572da4ea95457fb8705
Timestamp: 1714812201 Timestamp [UCT]: 2024-05-04 08:43:21 Age [y:d:h:m:s]: 00:194:00:22:52
Block: 1014553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138871 RingCT/type: yes/0
Extra: 01568d8b89ed95c9b004c51c72a3f3299369c9d49a28a04572da4ea95457fb87050211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd7ff3194bd6c692dc2cde58c74409a2b3ff2404b693dff69a2ac2c81aca9953 0.600000000000 1477674 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": 1014563, "vin": [ { "gen": { "height": 1014553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd7ff3194bd6c692dc2cde58c74409a2b3ff2404b693dff69a2ac2c81aca9953" } } ], "extra": [ 1, 86, 141, 139, 137, 237, 149, 201, 176, 4, 197, 28, 114, 163, 243, 41, 147, 105, 201, 212, 154, 40, 160, 69, 114, 218, 78, 169, 84, 87, 251, 135, 5, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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