Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f41d94f6fde174df034dd30ddbf15b515ecd1a3b035943bc703b26dff8e43a9

Tx prefix hash: ca29058effc1445c7dbb467f8ad1bb6b5b74746af5eeef842f08e70e19eb2c0c
Tx public key: 784b988fd646d379195525e0a1716d8372dfd76f1aee019f78f1b92a14befee1
Timestamp: 1679077720 Timestamp [UCT]: 2023-03-17 18:28:40 Age [y:d:h:m:s]: 02:069:09:26:46
Block: 719184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571173 RingCT/type: yes/0
Extra: 01784b988fd646d379195525e0a1716d8372dfd76f1aee019f78f1b92a14befee10211000000015029cbac000000000000000000

1 output(s) for total of 2.541234517000 dcy

stealth address amount amount idx
00: f32ae7b2fc671a9ce296bff97c73fc727eb45af7e7b95e98ef68b3e016e2bd7e 2.541234517000 1163901 of 0

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": 719194, "vin": [ { "gen": { "height": 719184 } } ], "vout": [ { "amount": 2541234517, "target": { "key": "f32ae7b2fc671a9ce296bff97c73fc727eb45af7e7b95e98ef68b3e016e2bd7e" } } ], "extra": [ 1, 120, 75, 152, 143, 214, 70, 211, 121, 25, 85, 37, 224, 161, 113, 109, 131, 114, 223, 215, 111, 26, 238, 1, 159, 120, 241, 185, 42, 20, 190, 254, 225, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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