Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52f41aa3992aaa55b8a5d74ad9ee4d8ec71ccaa18bdd609e5bce75c962a5b0c4

Tx prefix hash: 9566d37812019a0f182b243e5e30be5790fe5b88d85404dd63e77b98d0df8208
Tx public key: 824fa03207251eb5ea5c16db5cf70f82de1efba5038a721c0eea8669123d6208
Timestamp: 1708705185 Timestamp [UCT]: 2024-02-23 16:19:45 Age [y:d:h:m:s]: 01:038:16:34:49
Block: 963918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288661 RingCT/type: yes/0
Extra: 01824fa03207251eb5ea5c16db5cf70f82de1efba5038a721c0eea8669123d620802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c0b0321b28bd84717620e545f17e5810d62b3fb8ebf45c0d417761f382b377e 0.600000000000 1423645 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": 963928, "vin": [ { "gen": { "height": 963918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c0b0321b28bd84717620e545f17e5810d62b3fb8ebf45c0d417761f382b377e" } } ], "extra": [ 1, 130, 79, 160, 50, 7, 37, 30, 181, 234, 92, 22, 219, 92, 247, 15, 130, 222, 30, 251, 165, 3, 138, 114, 28, 14, 234, 134, 105, 18, 61, 98, 8, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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