Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f0b689a05660184e00a084868518e41aa5dacaac719cb091af2a2fe8c8042d

Tx prefix hash: 5ec2e99c95eb3c1722643545f6cf080f9d453821a7d95398596211ed251275fc
Tx public key: 36e6bd70c00ae6afad251606b7b792e3d50e6f4540015fe962e2ba85564f17c3
Timestamp: 1700739400 Timestamp [UCT]: 2023-11-23 11:36:40 Age [y:d:h:m:s]: 01:032:07:53:29
Block: 897873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284501 RingCT/type: yes/0
Extra: 0136e6bd70c00ae6afad251606b7b792e3d50e6f4540015fe962e2ba85564f17c302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.650090789000 dcy

stealth address amount amount idx
00: 7aabc8a408b63de6c68f74318972b314e256eeb0193df534e7e308020965fab1 0.650090789000 1354270 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": 897883, "vin": [ { "gen": { "height": 897873 } } ], "vout": [ { "amount": 650090789, "target": { "key": "7aabc8a408b63de6c68f74318972b314e256eeb0193df534e7e308020965fab1" } } ], "extra": [ 1, 54, 230, 189, 112, 192, 10, 230, 175, 173, 37, 22, 6, 183, 183, 146, 227, 213, 14, 111, 69, 64, 1, 95, 233, 98, 226, 186, 133, 86, 79, 23, 195, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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