Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b7d263f861d23a2ca6599d568489de49adcc763a1c526d20c3bda014d861be3

Tx prefix hash: 4e7b635c4c2a3497ebd68375f106fb3da4dba283b6bd4a477eb231aff813a4d5
Tx public key: 696372c10bf38ad01caa27a9d46f673a96f1e7676886e8d8ebe0267ed33133aa
Timestamp: 1707140516 Timestamp [UCT]: 2024-02-05 13:41:56 Age [y:d:h:m:s]: 00:342:12:17:17
Block: 950927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245219 RingCT/type: yes/0
Extra: 01696372c10bf38ad01caa27a9d46f673a96f1e7676886e8d8ebe0267ed33133aa0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5378cccb3975dbd5e753d5db90d368620d9dda373adb3c0b400e9d1c78cd5457 0.600000000000 1409621 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": 950937, "vin": [ { "gen": { "height": 950927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5378cccb3975dbd5e753d5db90d368620d9dda373adb3c0b400e9d1c78cd5457" } } ], "extra": [ 1, 105, 99, 114, 193, 11, 243, 138, 208, 28, 170, 39, 169, 212, 111, 103, 58, 150, 241, 231, 103, 104, 134, 232, 216, 235, 224, 38, 126, 211, 49, 51, 170, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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