Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee2fb805ffc84dc27e5e72cea8812a7fa0aa88f38e783746d53d086e376c65a

Tx prefix hash: cf44216fe05454695ec9a4cc2bc1eb8db83565768525a29b505bf9fa612232a3
Tx public key: e6e3932e0359c8fc4212943d2f6732661c97b147ce1cb411bb06f38d6f5dd74c
Timestamp: 1700996504 Timestamp [UCT]: 2023-11-26 11:01:44 Age [y:d:h:m:s]: 01:095:11:59:26
Block: 900001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329391 RingCT/type: yes/0
Extra: 01e6e3932e0359c8fc4212943d2f6732661c97b147ce1cb411bb06f38d6f5dd74c02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.639621513000 dcy

stealth address amount amount idx
00: 5b0345b139edbae0598561011384fb57aa37c913399a6b4a8a4148f60a607575 0.639621513000 1356476 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": 900011, "vin": [ { "gen": { "height": 900001 } } ], "vout": [ { "amount": 639621513, "target": { "key": "5b0345b139edbae0598561011384fb57aa37c913399a6b4a8a4148f60a607575" } } ], "extra": [ 1, 230, 227, 147, 46, 3, 89, 200, 252, 66, 18, 148, 61, 47, 103, 50, 102, 28, 151, 177, 71, 206, 28, 180, 17, 187, 6, 243, 141, 111, 93, 215, 76, 2, 17, 0, 0, 0, 10, 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