Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 331a8922dde4f44ad58aaf4920711446889a271ca499c4a2e55fba27f902aa96

Tx prefix hash: da4252cae37e28cb0d8cd302a60f4278c994087c0370eeff93bac56701c589db
Tx public key: e99c6f0c29d2691eae8a9f4aabc46f12bccefab9de1415c8428b7cbbc0957e8a
Timestamp: 1704913814 Timestamp [UCT]: 2024-01-10 19:10:14 Age [y:d:h:m:s]: 01:095:05:11:06
Block: 932471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329151 RingCT/type: yes/0
Extra: 01e99c6f0c29d2691eae8a9f4aabc46f12bccefab9de1415c8428b7cbbc0957e8a02110000000641ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d51d2cc471aefb67b1ffa615348de43e89b2329b773257856e56f9093ff45a6 0.600000000000 1390407 of 15

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": 932481, "vin": [ { "gen": { "height": 932471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d51d2cc471aefb67b1ffa615348de43e89b2329b773257856e56f9093ff45a6" } } ], "extra": [ 1, 233, 156, 111, 12, 41, 210, 105, 30, 174, 138, 159, 74, 171, 196, 111, 18, 188, 206, 250, 185, 222, 20, 21, 200, 66, 139, 124, 187, 192, 149, 126, 138, 2, 17, 0, 0, 0, 6, 65, 238, 28, 155, 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