Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6cb0b0aca5802669da6b5ff41222c8baaefd91b81774b338291ee968b838c9

Tx prefix hash: ba6cc2c3fb4409e8b4199bea56da2c220356c75cfddd2063c5c7a76369f4b84c
Tx public key: c476c9dfe10656920c132ea2c3a0ed1f450985eaf7ce07ae9615c449a2b5467f
Timestamp: 1580888764 Timestamp [UCT]: 2020-02-05 07:46:04 Age [y:d:h:m:s]: 05:273:17:33:06
Block: 59073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1345381 RingCT/type: yes/0
Extra: 01c476c9dfe10656920c132ea2c3a0ed1f450985eaf7ce07ae9615c449a2b5467f021100000001ff58ae94000000000000000000

1 output(s) for total of 391.081658542000 dcy

stealth address amount amount idx
00: 0173d85837ffe8aa6874cf79be057809f4754f9abae8b6ba19efb9857ec210e5 391.081658542000 109065 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": 59083, "vin": [ { "gen": { "height": 59073 } } ], "vout": [ { "amount": 391081658542, "target": { "key": "0173d85837ffe8aa6874cf79be057809f4754f9abae8b6ba19efb9857ec210e5" } } ], "extra": [ 1, 196, 118, 201, 223, 225, 6, 86, 146, 12, 19, 46, 162, 195, 160, 237, 31, 69, 9, 133, 234, 247, 206, 7, 174, 150, 21, 196, 73, 162, 181, 70, 127, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 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