Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0818e8ddedf518d3657d6786b08742022af131b5fc07d2d9486dc45e678d795

Tx prefix hash: 75d8168723e5766fb415ee13f15e78de325399e539409191bdb631726c8e5d6e
Tx public key: b4d2d6eaef7b05e809c45a7087d29e1dbf2d464a82b6b99db2aed5709f45bdb7
Timestamp: 1578667251 Timestamp [UCT]: 2020-01-10 14:40:51 Age [y:d:h:m:s]: 05:000:04:27:22
Block: 42775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150300 RingCT/type: yes/0
Extra: 01b4d2d6eaef7b05e809c45a7087d29e1dbf2d464a82b6b99db2aed5709f45bdb70211000000084ac5aa02000000000000000000

1 output(s) for total of 442.863116396000 dcy

stealth address amount amount idx
00: 7ae8a49ca2ac411d14a5b5ca3a826c457c976adaebfe49c5820d2eafa1d5c806 442.863116396000 77164 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": 42785, "vin": [ { "gen": { "height": 42775 } } ], "vout": [ { "amount": 442863116396, "target": { "key": "7ae8a49ca2ac411d14a5b5ca3a826c457c976adaebfe49c5820d2eafa1d5c806" } } ], "extra": [ 1, 180, 210, 214, 234, 239, 123, 5, 232, 9, 196, 90, 112, 135, 210, 158, 29, 191, 45, 70, 74, 130, 182, 185, 157, 178, 174, 213, 112, 159, 69, 189, 183, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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