Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d27b8967f3db63ffda139400d169d67c337c818f361cfefe2cfa18c83c348ce

Tx prefix hash: eae6382d85fa3b1d33a288c4b9710b82b063c6d3d5ae358293873c2069f1c6a1
Tx public key: e8e13bc0dcc4b987a9bd77e95fcee4fb5459d88e6e66f3a23b1eae607ca63a71
Timestamp: 1639285998 Timestamp [UCT]: 2021-12-12 05:13:18 Age [y:d:h:m:s]: 03:154:17:18:39
Block: 393685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 889359 RingCT/type: yes/0
Extra: 01e8e13bc0dcc4b987a9bd77e95fcee4fb5459d88e6e66f3a23b1eae607ca63a71021100000001117daff0000000000000000000

1 output(s) for total of 30.448843056000 dcy

stealth address amount amount idx
00: d0a924dd90a33bc251b81d7e26d609fe898093794bb0547a4442e6eb7c7aa928 30.448843056000 790998 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": 393695, "vin": [ { "gen": { "height": 393685 } } ], "vout": [ { "amount": 30448843056, "target": { "key": "d0a924dd90a33bc251b81d7e26d609fe898093794bb0547a4442e6eb7c7aa928" } } ], "extra": [ 1, 232, 225, 59, 192, 220, 196, 185, 135, 169, 189, 119, 233, 95, 206, 228, 251, 84, 89, 216, 142, 110, 102, 243, 162, 59, 30, 174, 96, 124, 166, 58, 113, 2, 17, 0, 0, 0, 1, 17, 125, 175, 240, 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