Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b3e3a5f436532a78469abe71ab05a4e0a283e65f5736667424b26bad9b56b03

Tx prefix hash: a4a0f28b409fa0a39f86ae379e929ad0c4d82954572b1755ab08e56aa519c29b
Tx public key: 21702e9087f2e630435ea012d2e13e36296a9b34ce47bdf310d2e975a37eaa3a
Timestamp: 1583209763 Timestamp [UCT]: 2020-03-03 04:29:23 Age [y:d:h:m:s]: 04:248:18:42:16
Block: 75183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1072209 RingCT/type: yes/0
Extra: 0121702e9087f2e630435ea012d2e13e36296a9b34ce47bdf310d2e975a37eaa3a0211000001504943cd9f000000000000000000

1 output(s) for total of 345.850420506000 dcy

stealth address amount amount idx
00: a745dfcd464f5d008773fe508c35bd1f5ffca69f7bff63a7ecf46b89a5124933 345.850420506000 139062 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": 75193, "vin": [ { "gen": { "height": 75183 } } ], "vout": [ { "amount": 345850420506, "target": { "key": "a745dfcd464f5d008773fe508c35bd1f5ffca69f7bff63a7ecf46b89a5124933" } } ], "extra": [ 1, 33, 112, 46, 144, 135, 242, 230, 48, 67, 94, 160, 18, 210, 225, 62, 54, 41, 106, 155, 52, 206, 71, 189, 243, 16, 210, 233, 117, 163, 126, 170, 58, 2, 17, 0, 0, 1, 80, 73, 67, 205, 159, 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