Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c0efc5142982e31b2a0f64bb55f2d623c384ecf3308e196c17ec04d7469064d

Tx prefix hash: 84264bddcea46716ee0bc4a751b38c4052398f1bd5016507fe91269e0cbaf191
Tx public key: f3e83a4e21386e1d50ac1e2cab6964d83d7bb3842a48f55944e07a4fa038b0be
Timestamp: 1702686244 Timestamp [UCT]: 2023-12-16 00:24:04 Age [y:d:h:m:s]: 01:151:13:55:51
Block: 914007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369507 RingCT/type: yes/0
Extra: 01f3e83a4e21386e1d50ac1e2cab6964d83d7bb3842a48f55944e07a4fa038b0be02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2945ea14333182007aaa89be617d0d9b522dd2359b245bc01779b68c658bbd 0.600000000000 1371287 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": 914017, "vin": [ { "gen": { "height": 914007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2945ea14333182007aaa89be617d0d9b522dd2359b245bc01779b68c658bbd" } } ], "extra": [ 1, 243, 232, 58, 78, 33, 56, 110, 29, 80, 172, 30, 44, 171, 105, 100, 216, 61, 123, 179, 132, 42, 72, 245, 89, 68, 224, 122, 79, 160, 56, 176, 190, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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