Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adb11a20989c6161663314a78200d9e9c06b04c067cf0d4388376405383ff4cb

Tx prefix hash: b9b8a2ef481784000a39d5e8fd7e87c6c23b6d14690f085d5f80c3c6f0f9975a
Tx public key: 71949d29f0c87792f09af2376011b60a4296d3034ea7f108e885756d9159cdb4
Timestamp: 1707699780 Timestamp [UCT]: 2024-02-12 01:03:00 Age [y:d:h:m:s]: 00:286:21:33:37
Block: 955572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205415 RingCT/type: yes/0
Extra: 0171949d29f0c87792f09af2376011b60a4296d3034ea7f108e885756d9159cdb40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e12cfaae195062328adce4e4456c2bb211741be31dc14b314d3a347e3642c6d2 0.600000000000 1414868 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": 955582, "vin": [ { "gen": { "height": 955572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e12cfaae195062328adce4e4456c2bb211741be31dc14b314d3a347e3642c6d2" } } ], "extra": [ 1, 113, 148, 157, 41, 240, 200, 119, 146, 240, 154, 242, 55, 96, 17, 182, 10, 66, 150, 211, 3, 78, 167, 241, 8, 232, 133, 117, 109, 145, 89, 205, 180, 2, 17, 0, 0, 0, 5, 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