Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c4ada08c60645cf81080b1093c3a4d6a362c86703627e8aa04e10d77d03ddea

Tx prefix hash: c0041db3a41694b256dec8feeed69cb8878f6d4ed799426f271dfad5276b5a23
Tx public key: 928e69f328f6b56bad07bfefb3b8b360bce86e0aff10b920498b216dd9dc2678
Timestamp: 1719015036 Timestamp [UCT]: 2024-06-22 00:10:36 Age [y:d:h:m:s]: 00:159:14:47:11
Block: 1049375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114258 RingCT/type: yes/0
Extra: 01928e69f328f6b56bad07bfefb3b8b360bce86e0aff10b920498b216dd9dc267802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e31f7666fc8cf3792308179dc91f122e9b8b711c0101f275fcc3f7d553b7cc9 0.600000000000 1519474 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": 1049385, "vin": [ { "gen": { "height": 1049375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e31f7666fc8cf3792308179dc91f122e9b8b711c0101f275fcc3f7d553b7cc9" } } ], "extra": [ 1, 146, 142, 105, 243, 40, 246, 181, 107, 173, 7, 191, 239, 179, 184, 179, 96, 188, 232, 110, 10, 255, 16, 185, 32, 73, 139, 33, 109, 217, 220, 38, 120, 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