Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24deb22ef795097f28df3ddf9e7d7a8f28ef97eab6865d5e6ddc4aa7e5290b7f

Tx prefix hash: e5b3426cbd434ba9ff7b51f8c47a7a31e5adc55420c26f8e242ba1c847dad3ed
Tx public key: 248bb936e073fbbaf3bb6a73181cc62e406ff40b3657fa335b41eccf55eedbde
Timestamp: 1734912786 Timestamp [UCT]: 2024-12-23 00:13:06 Age [y:d:h:m:s]: 00:177:09:43:09
Block: 1181101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126478 RingCT/type: yes/0
Extra: 01248bb936e073fbbaf3bb6a73181cc62e406ff40b3657fa335b41eccf55eedbde021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 974d2ac8b98c19666294f719fa160d2d6a1de9899e2c11ae07359d63c235c9cb 0.600000000000 1667516 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": 1181111, "vin": [ { "gen": { "height": 1181101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "974d2ac8b98c19666294f719fa160d2d6a1de9899e2c11ae07359d63c235c9cb" } } ], "extra": [ 1, 36, 139, 185, 54, 224, 115, 251, 186, 243, 187, 106, 115, 24, 28, 198, 46, 64, 111, 244, 11, 54, 87, 250, 51, 91, 65, 236, 207, 85, 238, 219, 222, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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