Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e689e046e6036c907b7b0bc82d566f377a7e3a4f6901ab44d46db99afd2e837

Tx prefix hash: 8c54c3eac5c2c498a6379c59e9c99c40d0ad522fb63c2b5e26a0f92bd87bf00c
Tx public key: f8c738919f61d29648f64046a6055735e767c560670f74f6148d090d67ccf222
Timestamp: 1584758220 Timestamp [UCT]: 2020-03-21 02:37:00 Age [y:d:h:m:s]: 04:294:02:36:12
Block: 85803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106855 RingCT/type: yes/0
Extra: 01f8c738919f61d29648f64046a6055735e767c560670f74f6148d090d67ccf2220211000000094943cd9f000000000000000000

1 output(s) for total of 318.944028709000 dcy

stealth address amount amount idx
00: e5057dcf400aa2860c26da6d88057ea5ce5a9100734ab529b4610a7c8e2d058d 318.944028709000 155019 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": 85813, "vin": [ { "gen": { "height": 85803 } } ], "vout": [ { "amount": 318944028709, "target": { "key": "e5057dcf400aa2860c26da6d88057ea5ce5a9100734ab529b4610a7c8e2d058d" } } ], "extra": [ 1, 248, 199, 56, 145, 159, 97, 210, 150, 72, 246, 64, 70, 166, 5, 87, 53, 231, 103, 197, 96, 103, 15, 116, 246, 20, 141, 9, 13, 103, 204, 242, 34, 2, 17, 0, 0, 0, 9, 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