Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559aee8530cdb0d94397de11b25d90e50288175d28a8b429a8d513936595b6ab

Tx prefix hash: be419abd9a10824ea351d5b0ec7dd50ab20043a73a2257623e338eb3aa41163b
Tx public key: e4e5416215d46b0cb5a66bd60f3901d683364df04c26802db67360befe64eb20
Timestamp: 1733787560 Timestamp [UCT]: 2024-12-09 23:39:20 Age [y:d:h:m:s]: 00:121:12:12:48
Block: 1171765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86631 RingCT/type: yes/0
Extra: 01e4e5416215d46b0cb5a66bd60f3901d683364df04c26802db67360befe64eb20021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e846d5d1af4bde7aa5aeeb8b5e9a476b9daab85260395ee0a5b0f5a63eb3cc01 0.600000000000 1657564 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": 1171775, "vin": [ { "gen": { "height": 1171765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e846d5d1af4bde7aa5aeeb8b5e9a476b9daab85260395ee0a5b0f5a63eb3cc01" } } ], "extra": [ 1, 228, 229, 65, 98, 21, 212, 107, 12, 181, 166, 107, 214, 15, 57, 1, 214, 131, 54, 77, 240, 76, 38, 128, 45, 182, 115, 96, 190, 254, 100, 235, 32, 2, 17, 0, 0, 0, 4, 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