Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5f4bb30ea1a15dc58f93771276cc5be766c743d92bd6c511f3bcc1d689f90e

Tx prefix hash: 67db21ab3262ef5ac775fa20e4b093cc60fe2acff9e89c04274130f365577fb3
Tx public key: 5f6cff5e93bac54e1afc35e969b82e39a8fc545a4091f238d01f6b0ce6137279
Timestamp: 1732691948 Timestamp [UCT]: 2024-11-27 07:19:08 Age [y:d:h:m:s]: 00:129:22:16:28
Block: 1162679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92671 RingCT/type: yes/0
Extra: 015f6cff5e93bac54e1afc35e969b82e39a8fc545a4091f238d01f6b0ce61372790211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95a02f79688bd0542d45e2005c53f66d92caca1cd423a7007a7e24164ad283e9 0.600000000000 1648336 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": 1162689, "vin": [ { "gen": { "height": 1162679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95a02f79688bd0542d45e2005c53f66d92caca1cd423a7007a7e24164ad283e9" } } ], "extra": [ 1, 95, 108, 255, 94, 147, 186, 197, 78, 26, 252, 53, 233, 105, 184, 46, 57, 168, 252, 84, 90, 64, 145, 242, 56, 208, 31, 107, 12, 230, 19, 114, 121, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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