Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82092bae5c8b9c5f4148fe9b270a19f1f99b79e06395615b9dc16146ec6e8090

Tx prefix hash: c7bc241faebcab244c477ef4c7e3b2047eeaaf63b6a68f3b332d57647d23a5aa
Tx public key: 5268603c9af6b7f77ba77d9a763952915d64919a4fd29684636ea438634c1c64
Timestamp: 1724412334 Timestamp [UCT]: 2024-08-23 11:25:34 Age [y:d:h:m:s]: 00:261:11:33:38
Block: 1094150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186747 RingCT/type: yes/0
Extra: 015268603c9af6b7f77ba77d9a763952915d64919a4fd29684636ea438634c1c64021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47e69d50017bf7f0f96ba8ba5b4a05b8fef4364b5b66c552b5db72b045a40730 0.600000000000 1569237 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": 1094160, "vin": [ { "gen": { "height": 1094150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47e69d50017bf7f0f96ba8ba5b4a05b8fef4364b5b66c552b5db72b045a40730" } } ], "extra": [ 1, 82, 104, 96, 60, 154, 246, 183, 247, 123, 167, 125, 154, 118, 57, 82, 145, 93, 100, 145, 154, 79, 210, 150, 132, 99, 110, 164, 56, 99, 76, 28, 100, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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