Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073a4cf89cdfeeea544c96ed3900dc3d197715e9c072de2a0d0eaf658d7ee46a

Tx prefix hash: bd28ad928d3445fff6dc170d36d9c0afb45e332cf04ebe46ebf99b3ec290563a
Tx public key: c76a89b01dbd0682a6decb33f4ccb3096364a3ba9bff868e8d095d2a6a5fbf70
Timestamp: 1722729923 Timestamp [UCT]: 2024-08-04 00:05:23 Age [y:d:h:m:s]: 00:279:01:59:50
Block: 1080187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199384 RingCT/type: yes/0
Extra: 01c76a89b01dbd0682a6decb33f4ccb3096364a3ba9bff868e8d095d2a6a5fbf70021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cc5571849e1a80e47ffe077ff8a57c4483a0bed22d558996a520f62355ed418 0.600000000000 1553452 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": 1080197, "vin": [ { "gen": { "height": 1080187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cc5571849e1a80e47ffe077ff8a57c4483a0bed22d558996a520f62355ed418" } } ], "extra": [ 1, 199, 106, 137, 176, 29, 189, 6, 130, 166, 222, 203, 51, 244, 204, 179, 9, 99, 100, 163, 186, 155, 255, 134, 142, 141, 9, 93, 42, 106, 95, 191, 112, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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