Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 662a061ab67e2f8ca806db87f98583221c07568031cb1cb2883c3b7a57f91e77

Tx prefix hash: f84a782a473ff48e54d2313c26d6829d92e996c3b79e60dcfb2a223dbd7dd93c
Tx public key: ae36c612c23c21c7a544becb1da64b2075dccf8d48abd0c98d8f6f991b18f4b5
Timestamp: 1732592402 Timestamp [UCT]: 2024-11-26 03:40:02 Age [y:d:h:m:s]: 00:118:16:11:53
Block: 1161854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84615 RingCT/type: yes/0
Extra: 01ae36c612c23c21c7a544becb1da64b2075dccf8d48abd0c98d8f6f991b18f4b5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b98da875eaa6f14be168846f2fc32b67ed3e78ad69e26163b2a476188088aed 0.600000000000 1647509 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": 1161864, "vin": [ { "gen": { "height": 1161854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b98da875eaa6f14be168846f2fc32b67ed3e78ad69e26163b2a476188088aed" } } ], "extra": [ 1, 174, 54, 198, 18, 194, 60, 33, 199, 165, 68, 190, 203, 29, 166, 75, 32, 117, 220, 207, 141, 72, 171, 208, 201, 141, 143, 111, 153, 27, 24, 244, 181, 2, 17, 0, 0, 0, 2, 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