Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0eccfdbc69076100d076bd9e2e44768d8784cbcc032504f21ed5eadb3ed3cd0

Tx prefix hash: 38405a0b78b0f371f14ddd4c01ef3f2f4030e3ed99b3cf4a6c1fab1b5078e38e
Tx public key: e0077a2060df3620919b8f401da7be33b75950ca345a4953990ec7b5dad0635d
Timestamp: 1577974911 Timestamp [UCT]: 2020-01-02 14:21:51 Age [y:d:h:m:s]: 04:360:22:22:34
Block: 37270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147024 RingCT/type: yes/0
Extra: 01e0077a2060df3620919b8f401da7be33b75950ca345a4953990ec7b5dad0635d02110000000cd81c26c0000000000000000000

1 output(s) for total of 461.859488361000 dcy

stealth address amount amount idx
00: f5c176e770d73b520ea4a3726edecfde0696510c0c3504694b5d832bcda2208d 461.859488361000 63210 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": 37280, "vin": [ { "gen": { "height": 37270 } } ], "vout": [ { "amount": 461859488361, "target": { "key": "f5c176e770d73b520ea4a3726edecfde0696510c0c3504694b5d832bcda2208d" } } ], "extra": [ 1, 224, 7, 122, 32, 96, 223, 54, 32, 145, 155, 143, 64, 29, 167, 190, 51, 183, 89, 80, 202, 52, 90, 73, 83, 153, 14, 199, 181, 218, 208, 99, 93, 2, 17, 0, 0, 0, 12, 216, 28, 38, 192, 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