Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 555ea5090c279fb18266a6d03bee3ec0a98a7c4ed784997f5894087f3885cdee

Tx prefix hash: 21819b0c36ed6271e81cfd822dfa8b777eb9ec60f98ad16c96f25e17b3060941
Tx public key: 699c860a19362c243dd4b8f8ba23fb6a4d8d93acd41d35707f533e637478bb74
Timestamp: 1706168168 Timestamp [UCT]: 2024-01-25 07:36:08 Age [y:d:h:m:s]: 00:349:18:23:46
Block: 942850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250434 RingCT/type: yes/0
Extra: 01699c860a19362c243dd4b8f8ba23fb6a4d8d93acd41d35707f533e637478bb7402110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e650ed26df5d41de035ae8a13fa905bcdb2401a37584e4daec8f4e36d2374dd9 0.600000000000 1401030 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": 942860, "vin": [ { "gen": { "height": 942850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e650ed26df5d41de035ae8a13fa905bcdb2401a37584e4daec8f4e36d2374dd9" } } ], "extra": [ 1, 105, 156, 134, 10, 25, 54, 44, 36, 61, 212, 184, 248, 186, 35, 251, 106, 77, 141, 147, 172, 212, 29, 53, 112, 127, 83, 62, 99, 116, 120, 187, 116, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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