Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5967b26d22ba10ae05d318792a327074894d9d418e9013887824efb00a14807d

Tx prefix hash: 65fd9ddac9c545cba1c9db3075df9a0022d5f4723597bbd73a2b403a5854c724
Tx public key: 93714d199cad9f0d4223d8e202b6d8582d1a9d9db9d3ac69515d6b3a4f3d3b7b
Timestamp: 1705196603 Timestamp [UCT]: 2024-01-14 01:43:23 Age [y:d:h:m:s]: 01:070:08:00:00
Block: 934811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311360 RingCT/type: yes/0
Extra: 0193714d199cad9f0d4223d8e202b6d8582d1a9d9db9d3ac69515d6b3a4f3d3b7b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66283f3f7560189531857a21a0fef9813f0ccb9c0e217e97be61def84fa9e3a2 0.600000000000 1392827 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": 934821, "vin": [ { "gen": { "height": 934811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66283f3f7560189531857a21a0fef9813f0ccb9c0e217e97be61def84fa9e3a2" } } ], "extra": [ 1, 147, 113, 77, 25, 156, 173, 159, 13, 66, 35, 216, 226, 2, 182, 216, 88, 45, 26, 157, 157, 185, 211, 172, 105, 81, 93, 107, 58, 79, 61, 59, 123, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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