Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2659681fe92b56acfe98dbcda8094b8eb2c5df349ec75e0f442041f76f32e42

Tx prefix hash: b8cbf70409a70bad986c1d70084bf6ae1706a5d68e7f68fcc817816c5a050915
Tx public key: f83c51cbc250d37cbbfc7d70c8dcc7b5eebf04f292e73b6bca6d363bc298083c
Timestamp: 1723869382 Timestamp [UCT]: 2024-08-17 04:36:22 Age [y:d:h:m:s]: 00:227:22:31:23
Block: 1089638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162761 RingCT/type: yes/0
Extra: 01f83c51cbc250d37cbbfc7d70c8dcc7b5eebf04f292e73b6bca6d363bc298083c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eba3b660b2f6a0ddcc66ac01ab5f6eace37b1a93ab6f727117096acf8b53aae 0.600000000000 1564261 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": 1089648, "vin": [ { "gen": { "height": 1089638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eba3b660b2f6a0ddcc66ac01ab5f6eace37b1a93ab6f727117096acf8b53aae" } } ], "extra": [ 1, 248, 60, 81, 203, 194, 80, 211, 124, 187, 252, 125, 112, 200, 220, 199, 181, 238, 191, 4, 242, 146, 231, 59, 107, 202, 109, 54, 59, 194, 152, 8, 60, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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