Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0beac8ec432e7e644e4dd303e8a75dd39e2cea571a342e9087d7d8415fb697

Tx prefix hash: 8d304df1687b7c3e676b6ae9918add106d2d9e7ab271ae1f128797f7c3d0fa57
Tx public key: 6865e4d938a471e419029f1d3d9c587e42b91fde97a5eb7eb139d75780f9cc12
Timestamp: 1697285071 Timestamp [UCT]: 2023-10-14 12:04:31 Age [y:d:h:m:s]: 01:177:23:55:02
Block: 869449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388241 RingCT/type: yes/0
Extra: 016865e4d938a471e419029f1d3d9c587e42b91fde97a5eb7eb139d75780f9cc1202110000000933af99f4000000000000000000

1 output(s) for total of 0.807522377000 dcy

stealth address amount amount idx
00: 9c57f5053e63d9c3ff5a467ffdc58888d61e06f77251c4d2c98d927093c11785 0.807522377000 1324294 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": 869459, "vin": [ { "gen": { "height": 869449 } } ], "vout": [ { "amount": 807522377, "target": { "key": "9c57f5053e63d9c3ff5a467ffdc58888d61e06f77251c4d2c98d927093c11785" } } ], "extra": [ 1, 104, 101, 228, 217, 56, 164, 113, 228, 25, 2, 159, 29, 61, 156, 88, 126, 66, 185, 31, 222, 151, 165, 235, 126, 177, 57, 215, 87, 128, 249, 204, 18, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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