Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f958eda3691999961ff471ad2c398064def860911e37f0f7fbfbd579ccda44ed

Tx prefix hash: 7246a7946d0f644c8556a418b8baf70b4fb901313812f552140616fbab83bbee
Tx public key: edf691cc6d35dc522667d1fb62c9c663df7519f6e6251173ee6b0b06b8353102
Timestamp: 1578739041 Timestamp [UCT]: 2020-01-11 10:37:21 Age [y:d:h:m:s]: 05:320:09:32:01
Block: 43198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1376847 RingCT/type: yes/0
Extra: 01edf691cc6d35dc522667d1fb62c9c663df7519f6e6251173ee6b0b06b835310202110000000d4ac5aa02000000000000000000

1 output(s) for total of 441.436191844000 dcy

stealth address amount amount idx
00: 4c426e52d06b4ac5609bcd0fab3c16ee5c9faabda16a8289d6454157c2ce027c 441.436191844000 78115 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": 43208, "vin": [ { "gen": { "height": 43198 } } ], "vout": [ { "amount": 441436191844, "target": { "key": "4c426e52d06b4ac5609bcd0fab3c16ee5c9faabda16a8289d6454157c2ce027c" } } ], "extra": [ 1, 237, 246, 145, 204, 109, 53, 220, 82, 38, 103, 209, 251, 98, 201, 198, 99, 223, 117, 25, 246, 230, 37, 17, 115, 238, 107, 11, 6, 184, 53, 49, 2, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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