Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78bb34bc24535e54a53aa49d39ac2697e88809e3506f3bc1c92f8fb2843b0649

Tx prefix hash: a3eff0e8186134ec28f6cb971ac4e80712c3a07200a29dcec000821ebc6f87f1
Tx public key: f5f80dcb089023bd428a551f131b87b2b2a8e21dc87044d31c3a39c8d234a7ed
Timestamp: 1723460230 Timestamp [UCT]: 2024-08-12 10:57:10 Age [y:d:h:m:s]: 00:231:17:59:29
Block: 1086244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165510 RingCT/type: yes/0
Extra: 01f5f80dcb089023bd428a551f131b87b2b2a8e21dc87044d31c3a39c8d234a7ed02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 064df0e0b54f83a22e9aefd8b6d15fb18030af8516cb59993c22c0740a8dce6d 0.600000000000 1560839 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": 1086254, "vin": [ { "gen": { "height": 1086244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "064df0e0b54f83a22e9aefd8b6d15fb18030af8516cb59993c22c0740a8dce6d" } } ], "extra": [ 1, 245, 248, 13, 203, 8, 144, 35, 189, 66, 138, 85, 31, 19, 27, 135, 178, 178, 168, 226, 29, 200, 112, 68, 211, 28, 58, 57, 200, 210, 52, 167, 237, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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