Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17df805742b3a64477a556e7343a9692c1cca9b5c45e0abfd48fcdb727d4c2cb

Tx prefix hash: 2632dd5596018fe90284b04da5ecec36c22f018e4778b260bd9c2cb897c3be65
Tx public key: ea35d22778c79aa8a2221d429e9cd0bd5aca0fd0983ea53c7c681d24ecb52b75
Timestamp: 1578941815 Timestamp [UCT]: 2020-01-13 18:56:55 Age [y:d:h:m:s]: 05:027:13:46:18
Block: 44892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169785 RingCT/type: yes/0
Extra: 01ea35d22778c79aa8a2221d429e9cd0bd5aca0fd0983ea53c7c681d24ecb52b75021100000073ff58ae94000000000000000000

1 output(s) for total of 435.767672516000 dcy

stealth address amount amount idx
00: 0ceb38557752c3c37876361fca9204d284896f66f4afea5e2a0dee19d4f29cdb 435.767672516000 81846 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": 44902, "vin": [ { "gen": { "height": 44892 } } ], "vout": [ { "amount": 435767672516, "target": { "key": "0ceb38557752c3c37876361fca9204d284896f66f4afea5e2a0dee19d4f29cdb" } } ], "extra": [ 1, 234, 53, 210, 39, 120, 199, 154, 168, 162, 34, 29, 66, 158, 156, 208, 189, 90, 202, 15, 208, 152, 62, 165, 60, 124, 104, 29, 36, 236, 181, 43, 117, 2, 17, 0, 0, 0, 115, 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