Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3eef0f5e1c17b0cca442252b12e25b1cadca48269a784957cab841bbc54d06

Tx prefix hash: 3216f32e9cbf98dc53ac811cb381aa24ac94290931d6f93cdb6b1556f3945d47
Tx public key: f14c1974007419dfedad5a9b6ee4ce881a88093c80e840729c18db89b208cfa5
Timestamp: 1731824530 Timestamp [UCT]: 2024-11-17 06:22:10 Age [y:d:h:m:s]: 00:362:17:46:21
Block: 1155482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256811 RingCT/type: yes/0
Extra: 01f14c1974007419dfedad5a9b6ee4ce881a88093c80e840729c18db89b208cfa5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14376904274e2e94d64c10a7e9c69b706d0ee32c6d0f2e9ef4fb0655ddec9e57 0.600000000000 1641099 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": 1155492, "vin": [ { "gen": { "height": 1155482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14376904274e2e94d64c10a7e9c69b706d0ee32c6d0f2e9ef4fb0655ddec9e57" } } ], "extra": [ 1, 241, 76, 25, 116, 0, 116, 25, 223, 237, 173, 90, 155, 110, 228, 206, 136, 26, 136, 9, 60, 128, 232, 64, 114, 156, 24, 219, 137, 178, 8, 207, 165, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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