Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b391a668577b9d35868ac2316cf2c3c9d304d004ce5d6c2434a6f8ca3847b5b8

Tx prefix hash: c5c1f43b652506d9275f8ce9ecd5d62bc2d1b84aceedb73536fb4ef0a2dfa9ee
Tx public key: 363e7beeddec29fd79bd48ed650e71becbf53fd413d98670fe5dfa1d6b1462ca
Timestamp: 1696538652 Timestamp [UCT]: 2023-10-05 20:44:12 Age [y:d:h:m:s]: 01:039:14:17:40
Block: 863248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289524 RingCT/type: yes/0
Extra: 01363e7beeddec29fd79bd48ed650e71becbf53fd413d98670fe5dfa1d6b1462ca02110000000333af99f4000000000000000000

1 output(s) for total of 0.846644442000 dcy

stealth address amount amount idx
00: c3d104405eb61a953aa8d99d0b21bc59f4ae315dbc23d885936db592ea45a569 0.846644442000 1317698 of 0

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": 863258, "vin": [ { "gen": { "height": 863248 } } ], "vout": [ { "amount": 846644442, "target": { "key": "c3d104405eb61a953aa8d99d0b21bc59f4ae315dbc23d885936db592ea45a569" } } ], "extra": [ 1, 54, 62, 123, 238, 221, 236, 41, 253, 121, 189, 72, 237, 101, 14, 113, 190, 203, 245, 63, 212, 19, 217, 134, 112, 254, 93, 250, 29, 107, 20, 98, 202, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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