Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae76d917378378aa5cb9aefa8c9d345e783da59292ef243fdd42e9e5f9d0d3e9

Tx prefix hash: aa9630d905192648cd26931cd4270e9d61cc59593b13c67d8ac3cf69d9b2c96b
Tx public key: 1b52cc4061768bdeb20df8638bed859a47d260a6a8e2694a37947c13a5e21677
Timestamp: 1701923489 Timestamp [UCT]: 2023-12-07 04:31:29 Age [y:d:h:m:s]: 01:158:08:07:15
Block: 907691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374331 RingCT/type: yes/0
Extra: 011b52cc4061768bdeb20df8638bed859a47d260a6a8e2694a37947c13a5e21677021100000010faf35c9c000000000000000000

1 output(s) for total of 0.603174383000 dcy

stealth address amount amount idx
00: b566c97ba7ea0e3fcab09db0d3e8873ccc6800ed419211848f85e97e416bac9a 0.603174383000 1364684 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": 907701, "vin": [ { "gen": { "height": 907691 } } ], "vout": [ { "amount": 603174383, "target": { "key": "b566c97ba7ea0e3fcab09db0d3e8873ccc6800ed419211848f85e97e416bac9a" } } ], "extra": [ 1, 27, 82, 204, 64, 97, 118, 139, 222, 178, 13, 248, 99, 139, 237, 133, 154, 71, 210, 96, 166, 168, 226, 105, 74, 55, 148, 124, 19, 165, 226, 22, 119, 2, 17, 0, 0, 0, 16, 250, 243, 92, 156, 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