Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d2c3366e07d99cd2af590445020d62dddb1471a94da524b13dc90c6253e7dba

Tx prefix hash: 6bf600e3ef56897fcb29aabebb570bae2cb1c262ff8465776cd8815fa5fc7616
Tx public key: 5b2d195d58ae891d92ac3e961ac1bd860634d33e71b8efc56f025fe882135e5b
Timestamp: 1711602798 Timestamp [UCT]: 2024-03-28 05:13:18 Age [y:d:h:m:s]: 00:354:07:23:23
Block: 987957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253315 RingCT/type: yes/0
Extra: 015b2d195d58ae891d92ac3e961ac1bd860634d33e71b8efc56f025fe882135e5b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c74d09f75a949d1a80f9e0b9157827345362bb2bd7c631bbbfd2e1280b82b127 0.600000000000 1448218 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": 987967, "vin": [ { "gen": { "height": 987957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c74d09f75a949d1a80f9e0b9157827345362bb2bd7c631bbbfd2e1280b82b127" } } ], "extra": [ 1, 91, 45, 25, 93, 88, 174, 137, 29, 146, 172, 62, 150, 26, 193, 189, 134, 6, 52, 211, 62, 113, 184, 239, 197, 111, 2, 95, 232, 130, 19, 94, 91, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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