Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656236453395e137661bbfaf5e2510ce7e1dfe215cb37cc1006806f57e1005ec

Tx prefix hash: 8cb9f52021d68bfa5b4c2184c2c8ea6733b78f218cbff54440ea3e46b1002333
Tx public key: aff3d7c54de1587187a8edd006231dc6664710feb85a8e7d9d05978e929317c6
Timestamp: 1734943934 Timestamp [UCT]: 2024-12-23 08:52:14 Age [y:d:h:m:s]: 00:335:02:18:06
Block: 1181357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236987 RingCT/type: yes/0
Extra: 01aff3d7c54de1587187a8edd006231dc6664710feb85a8e7d9d05978e929317c60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 008d3e0e2c6c029730d3238e1b397158e807b2f457cdc34c5ec5bbac6856c064 0.600000000000 1667776 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": 1181367, "vin": [ { "gen": { "height": 1181357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "008d3e0e2c6c029730d3238e1b397158e807b2f457cdc34c5ec5bbac6856c064" } } ], "extra": [ 1, 175, 243, 215, 197, 77, 225, 88, 113, 135, 168, 237, 208, 6, 35, 29, 198, 102, 71, 16, 254, 184, 90, 142, 125, 157, 5, 151, 142, 146, 147, 23, 198, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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