Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc0fd37a8aea26927403e9c1bcfce9ac92203602e8a88f2f3590695732631183

Tx prefix hash: bba5a9e207f2dd11208c7bd52322602ed4d3ef962b5f1b01c18faa72919dab4d
Tx public key: 3c87cfc7f189a23ef3472abce13e4b26ae4b39442bbe88ef9aa62347f12a55fd
Timestamp: 1697081214 Timestamp [UCT]: 2023-10-12 03:26:54 Age [y:d:h:m:s]: 01:092:14:31:34
Block: 867758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327428 RingCT/type: yes/0
Extra: 013c87cfc7f189a23ef3472abce13e4b26ae4b39442bbe88ef9aa62347f12a55fd0211000000024b8f5122000000000000000000

1 output(s) for total of 0.818008004000 dcy

stealth address amount amount idx
00: bd79488f33281d1a2e11f476020f8be64fc15325c375d45c339e66307aa43981 0.818008004000 1322474 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": 867768, "vin": [ { "gen": { "height": 867758 } } ], "vout": [ { "amount": 818008004, "target": { "key": "bd79488f33281d1a2e11f476020f8be64fc15325c375d45c339e66307aa43981" } } ], "extra": [ 1, 60, 135, 207, 199, 241, 137, 162, 62, 243, 71, 42, 188, 225, 62, 75, 38, 174, 75, 57, 68, 43, 190, 136, 239, 154, 166, 35, 71, 241, 42, 85, 253, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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