Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8560a266e0e217c28a9937e228c05450a03ea4dd2e794dc9712764a6e6ea36d

Tx prefix hash: b4c84b22da6998e173fbe389dac68c9b4571cb85e90d91a75278d83e1a0cb228
Tx public key: b234c799fc19ce67adc0aa96b56e9bb622d0048ffbe18bd69fcb733ebed22092
Timestamp: 1689914641 Timestamp [UCT]: 2023-07-21 04:44:01 Age [y:d:h:m:s]: 01:242:17:30:59
Block: 808392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434604 RingCT/type: yes/0
Extra: 01b234c799fc19ce67adc0aa96b56e9bb622d0048ffbe18bd69fcb733ebed22092021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.286654200000 dcy

stealth address amount amount idx
00: ec5a0822581f9c34d931c1ebdf11b4c7f0b095e11cf48a865d5bdb9dc33297dd 1.286654200000 1259967 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": 808402, "vin": [ { "gen": { "height": 808392 } } ], "vout": [ { "amount": 1286654200, "target": { "key": "ec5a0822581f9c34d931c1ebdf11b4c7f0b095e11cf48a865d5bdb9dc33297dd" } } ], "extra": [ 1, 178, 52, 199, 153, 252, 25, 206, 103, 173, 192, 170, 150, 181, 110, 155, 182, 34, 208, 4, 143, 251, 225, 139, 214, 159, 203, 115, 62, 190, 210, 32, 146, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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