Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63a738b2f1cbf37b3507a928d25a18fba47f7d9592deb45fe7139a36808403cc

Tx prefix hash: 7f2e681a7929267a9155e947ed72b56fe5a2ff97cd1fd403f5fe08405b058e40
Tx public key: a0cd8411bd99ed059fff58267f722de96f4247c7e5cfdc0fd17c017f274b1dc4
Timestamp: 1609317208 Timestamp [UCT]: 2020-12-30 08:33:28 Age [y:d:h:m:s]: 04:283:09:52:07
Block: 171995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213628 RingCT/type: yes/0
Extra: 01a0cd8411bd99ed059fff58267f722de96f4247c7e5cfdc0fd17c017f274b1dc4021100000010a45716b1000000000000000000

1 output(s) for total of 165.255111800000 dcy

stealth address amount amount idx
00: 5ba4bb5154a6593fccc66e23da3e1eac98a30242f2f593e6309beb25e341098d 165.255111800000 324738 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": 172005, "vin": [ { "gen": { "height": 171995 } } ], "vout": [ { "amount": 165255111800, "target": { "key": "5ba4bb5154a6593fccc66e23da3e1eac98a30242f2f593e6309beb25e341098d" } } ], "extra": [ 1, 160, 205, 132, 17, 189, 153, 237, 5, 159, 255, 88, 38, 127, 114, 45, 233, 111, 66, 71, 199, 229, 207, 220, 15, 209, 124, 1, 127, 39, 75, 29, 196, 2, 17, 0, 0, 0, 16, 164, 87, 22, 177, 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