Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fcad32701ec01be292f1efb9c9505fca7fd98f915d5cbdccbf19d1549978a92

Tx prefix hash: 552bce5c86d43ec23e96563869040ff9f7d7614bfc4a21d74d0df08f801212ac
Tx public key: 0a4ce29d459e531a6eae0b6442ba57117eb6668e043d5678c128f51a8f946beb
Timestamp: 1649031074 Timestamp [UCT]: 2022-04-04 00:11:14 Age [y:d:h:m:s]: 03:211:12:37:01
Block: 472635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 929303 RingCT/type: yes/0
Extra: 010a4ce29d459e531a6eae0b6442ba57117eb6668e043d5678c128f51a8f946beb02110000000aa8c141c5000000000000000000

1 output(s) for total of 16.671101301000 dcy

stealth address amount amount idx
00: 33f5bc94ccaccaece857721a031de582b50ccf6382f2dda29be8b6486298bf9e 16.671101301000 892292 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": 472645, "vin": [ { "gen": { "height": 472635 } } ], "vout": [ { "amount": 16671101301, "target": { "key": "33f5bc94ccaccaece857721a031de582b50ccf6382f2dda29be8b6486298bf9e" } } ], "extra": [ 1, 10, 76, 226, 157, 69, 158, 83, 26, 110, 174, 11, 100, 66, 186, 87, 17, 126, 182, 102, 142, 4, 61, 86, 120, 193, 40, 245, 26, 143, 148, 107, 235, 2, 17, 0, 0, 0, 10, 168, 193, 65, 197, 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