Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d4cd09e23e00b4066a155ce81ab635c14fab0b51231d8300524c5a085cf6bb0

Tx prefix hash: 23a0eeefd4a9c62e9f752752a8a5836eac3c77fee1a71978ea7543712716fa13
Tx public key: b7a7e962fdd7aa6d9b4e20dbcc2a16cacf4acba0186da4b30f1afd4c14d43c61
Timestamp: 1726497872 Timestamp [UCT]: 2024-09-16 14:44:32 Age [y:d:h:m:s]: 00:180:22:44:32
Block: 1111424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129166 RingCT/type: yes/0
Extra: 01b7a7e962fdd7aa6d9b4e20dbcc2a16cacf4acba0186da4b30f1afd4c14d43c61021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a70f7213d352cec99b6a6a4a28e90b3bf0621c56b7c167f2a260e39f955c8127 0.600000000000 1590377 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": 1111434, "vin": [ { "gen": { "height": 1111424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a70f7213d352cec99b6a6a4a28e90b3bf0621c56b7c167f2a260e39f955c8127" } } ], "extra": [ 1, 183, 167, 233, 98, 253, 215, 170, 109, 155, 78, 32, 219, 204, 42, 22, 202, 207, 74, 203, 160, 24, 109, 164, 179, 15, 26, 253, 76, 20, 212, 60, 97, 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