Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10990a424a84cd88acbb584f4232f3ac6d94e9f5b363a3a703b7fc5420840e2e

Tx prefix hash: f674e76d4fd9b88df940a49f7410efe1348e782c43ccc4e096cb85e652e757bd
Tx public key: 9d3cb5da8a28881ecb03347f975d0dda4e20b1cde56b2b69bdf12b9d8586b5cf
Timestamp: 1574570608 Timestamp [UCT]: 2019-11-24 04:43:28 Age [y:d:h:m:s]: 05:172:19:16:50
Block: 16179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1266190 RingCT/type: yes/0
Extra: 019d3cb5da8a28881ecb03347f975d0dda4e20b1cde56b2b69bdf12b9d8586b5cf021100000002f95225a5000000000000000000

1 output(s) for total of 542.491751516000 dcy

stealth address amount amount idx
00: f80fa7ef885039168ba8909c0254a4e91beb102c6ba2e381268683dc2d7aef6c 542.491751516000 22431 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": 16189, "vin": [ { "gen": { "height": 16179 } } ], "vout": [ { "amount": 542491751516, "target": { "key": "f80fa7ef885039168ba8909c0254a4e91beb102c6ba2e381268683dc2d7aef6c" } } ], "extra": [ 1, 157, 60, 181, 218, 138, 40, 136, 30, 203, 3, 52, 127, 151, 93, 13, 218, 78, 32, 177, 205, 229, 107, 43, 105, 189, 241, 43, 157, 133, 134, 181, 207, 2, 17, 0, 0, 0, 2, 249, 82, 37, 165, 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