Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68ec08a4e2c6e7d75bb17970616ea29ea356dcf1b03b2aa3c63826454eae7e31

Tx prefix hash: ca52d3e8b55363a96f332e120e45f646e01063e2622c65baa474e6553d999b72
Tx public key: bf7cee7883d69be1efb5281a7058daf040163471c1f0328123b154d53fe585c6
Timestamp: 1739151750 Timestamp [UCT]: 2025-02-10 01:42:30 Age [y:d:h:m:s]: 00:346:00:24:33
Block: 1215892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245005 RingCT/type: yes/0
Extra: 01bf7cee7883d69be1efb5281a7058daf040163471c1f0328123b154d53fe585c6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 698bb694e17cf621c89e177b698192ea277d5a409a649ae6d13f6498c6a9d3f0 0.600000000000 1702691 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": 1215902, "vin": [ { "gen": { "height": 1215892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "698bb694e17cf621c89e177b698192ea277d5a409a649ae6d13f6498c6a9d3f0" } } ], "extra": [ 1, 191, 124, 238, 120, 131, 214, 155, 225, 239, 181, 40, 26, 112, 88, 218, 240, 64, 22, 52, 113, 193, 240, 50, 129, 35, 177, 84, 213, 63, 229, 133, 198, 2, 17, 0, 0, 0, 3, 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