Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb512e7ba17b68108fd963ed01f21693ca1d82f0410d9a84331d117e93581993

Tx prefix hash: 6a518f6a3703d0e1ed5da20ccc6e5eda1aa3073f7584d2796896ba3428b3f4c1
Tx public key: 707ffb9f17ae683237d6fc8eef1e9367a3e24a6336d02b0325643da732840305
Timestamp: 1735649425 Timestamp [UCT]: 2024-12-31 12:50:25 Age [y:d:h:m:s]: 00:355:08:00:22
Block: 1187165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251511 RingCT/type: yes/0
Extra: 01707ffb9f17ae683237d6fc8eef1e9367a3e24a6336d02b0325643da73284030502110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beca985c87720fcb14e196d8d241d03577d7b71362922b96f8463b088e7afe15 0.600000000000 1673652 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": 1187175, "vin": [ { "gen": { "height": 1187165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beca985c87720fcb14e196d8d241d03577d7b71362922b96f8463b088e7afe15" } } ], "extra": [ 1, 112, 127, 251, 159, 23, 174, 104, 50, 55, 214, 252, 142, 239, 30, 147, 103, 163, 226, 74, 99, 54, 208, 43, 3, 37, 100, 61, 167, 50, 132, 3, 5, 2, 17, 0, 0, 0, 11, 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