Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68e5b54084334e20548d4db3ee01c62c42b0d1781d71f96c63a42f93822e0fc8

Tx prefix hash: 41c9bb840e6e884119fa2966bd1f3f936befd143134dd28623f885e5a24a1277
Tx public key: 472fbf20fc5c3a882b75550944963bf4f7b50af8a1f7f46f10c1224b690fd28a
Timestamp: 1578916768 Timestamp [UCT]: 2020-01-13 11:59:28 Age [y:d:h:m:s]: 05:028:03:32:05
Block: 44562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170317 RingCT/type: yes/0
Extra: 01472fbf20fc5c3a882b75550944963bf4f7b50af8a1f7f46f10c1224b690fd28a0211000000b0ff58ae94000000000000000000

1 output(s) for total of 436.871341351000 dcy

stealth address amount amount idx
00: 27de28bed6d8a395a50b47aa7d75a087918aa852a08c7f514e0aa15d5fdcb959 436.871341351000 81126 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": 44572, "vin": [ { "gen": { "height": 44562 } } ], "vout": [ { "amount": 436871341351, "target": { "key": "27de28bed6d8a395a50b47aa7d75a087918aa852a08c7f514e0aa15d5fdcb959" } } ], "extra": [ 1, 71, 47, 191, 32, 252, 92, 58, 136, 43, 117, 85, 9, 68, 150, 59, 244, 247, 181, 10, 248, 161, 247, 244, 111, 16, 193, 34, 75, 105, 15, 210, 138, 2, 17, 0, 0, 0, 176, 255, 88, 174, 148, 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