Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c75405212344723ca326020ee67fab285aa9def1a662e0136d0c7849ec8ec761

Tx prefix hash: 5e4dec38f36ae71ef64df48f4307ecf81ba2cc9c010b24eeb50cd6e3b74af0f6
Tx public key: 0b9d72d4e865a508b9a38b19675c2a1ab72fc9f08627de1cf8e6963b35b6a210
Timestamp: 1708280718 Timestamp [UCT]: 2024-02-18 18:25:18 Age [y:d:h:m:s]: 01:055:02:59:02
Block: 960396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300435 RingCT/type: yes/0
Extra: 010b9d72d4e865a508b9a38b19675c2a1ab72fc9f08627de1cf8e6963b35b6a2100211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a52af1db89488826f10aa716e0329d3f62b09bb2bb649034e88c58acfae73394 0.600000000000 1419959 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": 960406, "vin": [ { "gen": { "height": 960396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a52af1db89488826f10aa716e0329d3f62b09bb2bb649034e88c58acfae73394" } } ], "extra": [ 1, 11, 157, 114, 212, 232, 101, 165, 8, 185, 163, 139, 25, 103, 92, 42, 26, 183, 47, 201, 240, 134, 39, 222, 28, 248, 230, 150, 59, 53, 182, 162, 16, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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